Business rules compliance
| Characteristic Name: | Business rules compliance |
| Dimension: | Validity |
| Description: | Data should comply with business rules |
| Granularity: | Element |
| Implementation Type: | Rule-based approach |
| Characteristic Type: | Declarative |
Verification Metric:
| The number of tasks failed or under performed due to lack of data precision |
| The number of complaints received due to lack of data precision |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Identify data related business rules separately (business rules that determines the value of data elements and business rules that get executed depending on the values of data elements) and organise them into a separate executable data rules engine | (1) The system maintains price routines to handle price related data Element :Discount rate A price routine (procedure) can be maintained to calculate the discount rate considering the rules R1:All registered customers get a discount of 6% |
| Implement a stewardship structure for business rules (parallel to stewardship structure for data) and manage the changes to the rules properly | (1) Sales director is responsible for discounts and his approval is needed to change a discount rate. Only the sales manager can change the rules related to discounts. |
| Maintain an error log to identify the problems resulted in the data rules repository where the problematic data records can be identified precisely | (1) Rules engines |
| Continuously monitor the root causes for the errors recorded in the log and take preventive actions by amending the rules, fixing the technical defects in the system etc. | (1) Some trip data is missing for a particular journey in the go card system and as a result an unacceptable journey duration was resulted. New rules were implemented to process such data using a different criteria |
Validation Metric:
| How mature is the creation and implementation of the data related business rules |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| One common example in education is the student school of record. While most students do not change schools during an academic year, many do, especially in urban settings. Thus, the school at which students are tested may not be the school at which they received most of their instruction. Because school-level student achievement measures become increasingly invalid as the number of mobile students increases, many districts will hold schools accountable only for those students who were enrolled for a full academic year. In this case, student achievement measures for a given school lose validity as the percentage of mobile students increases. | J. G. Watson, S. B. Kraemer, and C. A. Thorn, “Data Quality Essentials. Guide to Implementation: Resources for Applied Practice”, August 2009. |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| Determines the extent to which data is not missing important relationship linkages. For example, the launch date for a new product must be valid and must be the first week of any quarter, since all new products are launched in the first week of each quarter. | D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008. |
| 1) Data values conform to the Specified Business Rules.
2) A derived or calculated data value is Produced Correctly according to a specified Calculation Formula or set of Derivation Rules. |
ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing. |
Continuity of data access
| Characteristic Name: | Continuity of data access |
| Dimension: | Availability and Accessability |
| Description: | The technology infrastructure should not prohibit the speed and continuity of access to the data for the users |
| Granularity: | Information object |
| Implementation Type: | Process-bases approacd |
| Characteristic Type: | Usage |
Verification Metric:
| The number of tasks failed or under performed due to the lack of continuity in data access |
| The number of complaints received due to lack of continuity in data access |
The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation
| Guidelines: | Scenario: |
|---|---|
| Convenient and efficient platform should be made available to access data depending on the task at hand | (1) For a sales person, a web based interface run on a smart device is more suitable to quickly access data |
| Speed of the data retrieval should be acceptable for users working pace | (1) For an online customer care executive, speedy retrieval of information is necessary since the customer cannot be kept waiting (2) With the growth of the database reports become slower (Anti example) |
| Continuous and unobstructed connectivity should be ensured for data retrievals | (1) Connection lost while accessing reports (Anti example) |
| Proper concurrency control has been implemented | (1) Controlling access to data by locks |
| Technological changes in the infrastructure/system should be handled in such a way that they should not make data inaccessible | (1) New version of the software does not provide access to " X out orders" since the new version does not allow the function "X out" |
Validation Metric:
| How mature is the process of maintaining an infrastructure for data access |
These are examples of how the characteristic might occur in a database.
| Example: | Source: |
|---|---|
| 1) For example, recording the age and race in medical records may be appropriate.
However, it may be illegal to collect this information in human resources departments. 2) For example, the best and easiest method to obtain demographic information may be to obtain it from an existing system. Another method may be to assign data collection by the expertise of each team member. For example, the admission staff collects demographic data, the nursing staff collects symptoms, and the HIM staff assigns codes. Team members should be assigned accordingly. |
B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6). |
The Definitions are examples of the characteristic that appear in the sources provided.
| Definition: | Source: |
|---|---|
| 1) Is there a continuous and unobstructed way to get to the information?
2) Can the infrastructure match the user’s working pace? |
EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer. |
| Data is easy and quick to retrieve. | PRICE, R. J. & SHANKS, G. Empirical refinement of a semiotic information quality framework. System Sciences, 2005. HICSS'05. Proceedings of the 38th Annual Hawaii International Conference on, 2005. IEEE, 216a-216a. |
| 1) availability of a data source or a system.
2) Accessibility expresses how much data are available or quickly retrievable. 3) The frequency of failures of a system, its fault tolerance. |
SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15. |